{
"hostname": "secure-paypal-account-verify.xyz",
"risk_score": 80,
"risk_level": "CRITICAL",
"is_safe": false
}
curl --location --request GET 'https://zylalabs.com/api/15202/dns+spf+dmarc+bimi+security+lookup+api/40670/analyze+url+for+phishing+and+brand+spoofing?url=https://secure-paypal-account-verify.xyz/login' --header 'Authorization: Bearer YOUR_API_KEY'
{
"domain": "stripe.com",
"dns_security_score": 95,
"spoofing_protection": "strong"
}
curl --location --request GET 'https://zylalabs.com/api/15202/dns+spf+dmarc+bimi+security+lookup+api/40671/inspect+deep+dns+and+email+security+records?domain=stripe.com' --header 'Authorization: Bearer YOUR_API_KEY'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the DNS SPF DMARC BIMI Security Lookup API simply include your bearer token in the Authorization header.
| Header | Description |
|---|---|
Authorization
|
Required
Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.
|
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
(Save 2 months with annual billing 🎉)
Detect phishing URLs, IDN punycode homograph attacks, and brand typosquatting, inspect deep DNS security records including SPF, DMARC, BIMI, and CAA, and audit password Shannon entropy.
It checks for IDN punycode homograph attacks, lookalike brand impersonation, high-abuse top-level domains, raw IP hosts, deep subdomain nesting, and credential lure keywords.
It resolves A, AAAA, MX, NS, TXT, CAA, SPF, DMARC, and BIMI records in real time to verify domain and email anti-spoofing posture.
It returns a JSON object containing the analyzed hostname, a numeric risk score from 0 to 100, a risk level such as CRITICAL, and an is_safe boolean. For example, a score of 80 with is_safe set to false indicates a high-risk destination.
Use risk_score for numeric ranking and risk_level for a readable classification. The is_safe field provides a direct boolean decision. Applications can block or flag results where is_safe is false, while security teams can use the score to prioritize investigation.
Submit a URL or domain for evaluation. The service analyzes the hostname and related URL characteristics, including suspicious naming patterns, brand impersonation signals, and credential-lure indicators. Use the complete URL when path or lure context is relevant.
It returns a JSON object with the queried domain, a dns_security_score, and a spoofing_protection classification. For example, stripe.com may return a score of 95 and the classification strong, indicating a well-configured email security posture.
The score provides a compact measure of a domain’s DNS and email protection posture. Use it to compare domains, identify weak configurations, prioritize remediation, or support onboarding and vendor-risk reviews. The spoofing_protection field supplies a human-readable summary.
Missing records can reduce the calculated security score or produce a weaker protection classification. Treat incomplete results as configuration findings rather than assuming the domain is malicious. Review the returned assessment and investigate the relevant DNS or email-security settings.
Use phishing analysis to assess whether a destination appears deceptive, then use DNS inspection to evaluate the domain’s infrastructure and email anti-spoofing posture. Combining risk_score, is_safe, dns_security_score, and spoofing_protection supports layered detection and triage.
Both endpoints return structured JSON objects with named fields rather than unstructured text. Values include strings such as hostname or domain, numeric scores, categorical labels, and booleans. Clients should parse fields by name and handle additional fields or classifications defensively.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund