Hostname
yadmanteb.com
Last fetched
yadmanteb.com resolves to 3 IPv4 addresses operated by CLOUDFLARENET - Cloudflare, Inc. in CA. WHOIS lists iana:1387 as the registrar.
Nutrition Label
Resolution chain
yadmanteb.com resolves to 3 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 104.21.81.187 | 104.21.80.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 172.67.163.100 | 172.67.160.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 5.144.130.73 | 5.144.130.0/24 | AS59441 | — | IR |
WHOIS identity
- Registrar
- iana:1387
- Organization
- frshad khsrvi
- Contact emails
Subdomains
10 observed subdomains of yadmanteb.com.
Web-graph footprint
Distinct hostnames that link to or from yadmanteb.com in the public web crawl.
25 sites link to this hostname.
46 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
- _dc-mx.05f10b84a6b5.yadmanteb.com
- yadmanteb.com
SPF policy
16 SPF mechanisms authorising senders for yadmanteb.com.
| Mechanism | Target |
|---|---|
| SPF_A | yadmanteb.com |
| SPF_INCLUDE | mailii.org |
| SPF_INCLUDE | spf.mailii.org |
| SPF_IP | 172.101.1.38 |
| SPF_IP | 185.165.31.12 |
| SPF_IP | 185.211.57.58 |
| SPF_IP | 185.211.59.13 |
| SPF_IP | 208.110.86.66/16 |
| SPF_IP | 208.74.123.2 |
| SPF_IP | 31.25.90.131 |
| SPF_IP | 62.204.61.118 |
| SPF_IP | 62.204.61.19 |
| SPF_IP | 62.204.61.22 |
| SPF_IP | 62.60.201.22 |
| SPF_IP | 89.39.208.174 |
| SPF_MX | yadmanteb.com |
Related pages
Pivot deeper into the graph from yadmanteb.com.
- IP · 104.21.81.187
- ASN · AS13335CLOUDFLARENET - Cloudflare, Inc.
- Registrar · iana:1387
- Country · CA
- Email · farshadkhosravi7@gmail.com
- TLD · .com
- Browse hostnames · ya…
- Glossary · What is a hostname?
- Whisper Internet Directory — home
- Live MOAS conflicts feed
- Threat feed · Spamhaus DROP
- United States internet infrastructure
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "yadmanteb.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.