Hostname
youmetalks.com
Last fetched
youmetalks.com resolves to 104.18.0.179, announced in 104.18.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. youmetalks.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 104.18.0.179
104.18.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.18.1.179
104.18.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:1387
- Registrant organisation
- c/o whoisproxy.com
- Contact emails
- 948b10a421@youmetalks.com.whoistrustee.com, 02b18ecbd83c80459f79fa42004e2a69a215eb7478ccdb8376ca1f54cdbd0282@youmetalks.com.whoisproxy.org, 5da96b31a8847fecbf51d6a1282448431de2f5671bc4a3d470168f2daf5ca394@youmetalks.com.whoisproxy.org, 65afcbb1ad386278cdf332bd223ed076adac130ece5f390cfa459a42a2fde8da@youmetalks.com.whoisproxy.org, 755c9353afb8f7caf3b5b364eca76a38fe3d812edb48f91d0871538b51612c75@youmetalks.com.whoisproxy.org, f0706538919fec0105fbed99cbcc6a31699d635bf7369145b6d89f5ac9b09104@youmetalks.com.whoisproxy.org, f333eaeeddd173e035cb4df9c60c7d7caf1e76b809492e5519f38098df6e30f3@youmetalks.com.whoisproxy.org
Subdomains
Showing 3 of 4. View all subdomains →
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
Nameservers
- heather.ns.cloudflare.com
- ned.ns.cloudflare.com
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
SPF policy
- include: _spf.google.com
- include: mail.zendesk.com
- include: spf.sendios.io
Threat-feed evidence
History
Related pages
Pivot from youmetalks.com into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "youmetalks.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.