Hostname
yet2.com
Last fetched
yet2.com resolves to 2 IPv4 addresses operated by CLOUDFLARENET - Cloudflare, Inc. in CA. WHOIS lists iana:2 as the registrar.
Nutrition Label
Resolution chain
yet2.com resolves to 2 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
| IP | Prefix | ASN | Operator | Country |
|---|---|---|---|---|
| 104.17.54.64 | 104.17.48.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
| 104.17.55.64 | 104.17.48.0/20 | AS13335 | CLOUDFLARENET - Cloudflare, Inc. | CA |
WHOIS identity
- Registrar
- iana:2
- Organization
- yet2.com,
- Contact emails
Subdomains
30 observed subdomains of yet2.com.
Showing 25 of 30. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from yet2.com in the public web crawl.
145 sites link to this hostname.
9 sites linked to from this hostname.
Sample inbound links
Threat posture
History
Mail and authentication
MX records
SPF policy
19 SPF mechanisms authorising senders for yet2.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | _spf.mlsend.com |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_INCLUDE | spf.spamhero.com |
| SPF_IP | 18.209.37.111 |
| SPF_IP | 2603:3005:36d4:9000:ad37:b11a:96c3:c848 |
| SPF_IP | 3.115.27.252 |
| SPF_IP | 3.230.252.149 |
| SPF_IP | 3.234.0.191 |
| SPF_IP | 34.192.246.84 |
| SPF_IP | 35.170.170.140 |
| SPF_IP | 50.212.22.6 |
| SPF_IP | 52.1.255.138 |
| SPF_IP | 52.18.135.154 |
| SPF_IP | 52.203.19.24 |
| SPF_IP | 52.45.87.104 |
| SPF_IP | 52.5.205.131 |
| SPF_IP | 54.73.6.148 |
| SPF_IP | 63.34.1.169 |
| SPF_IP | 99.80.54.106 |
Related pages
Pivot deeper into the graph from yet2.com.
- IP · 104.17.54.64
- ASN · AS13335CLOUDFLARENET - Cloudflare, Inc.
- Registrar · iana:2
- Country · CA
- Email · domainreg@yet2.com
- TLD · .com
- Browse hostnames · ye…
- 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: "yet2.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.