Hostname
it-caffe.com
Last fetched
it-caffe.com resolves to 128.0.136.85, announced in 128.0.128.0/20 by ASN-MGTS-USPD - PJSC Moscow city telephone network in RU. it-caffe.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
- 128.0.136.85
128.0.128.0/20 · ASN-MGTS-USPD - PJSC Moscow city telephone network
- 195.22.148.52
195.22.148.0/24 · Garant-Park-Internet - Garant-Park-Internet LLC · Moscow, RU
- 195.22.148.73
195.22.148.0/24 · Garant-Park-Internet - Garant-Park-Internet LLC · Moscow, RU
- 95.165.70.13
95.165.0.0/16 · ASN-MGTS-USPD - PJSC Moscow city telephone network · Moscow, RU
- 95.211.151.53
95.211.0.0/16 · LEASEWEB-NL-AMS-01 - LeaseWeb Netherlands B.V.
IPv6 resolution
No AAAA record for it-caffe.com is recorded in WhisperGraph.
Attribution
pjsc moscow city telephone
DNS_OPERATOR, ORIGIN_AS
WHOIS identity
- Registrar
- iana:1606
- Registrant organisation
- personal data, can not be publicly disclosed according to applicable laws.
- Contact emails
- contact@privacyprotect.org, project817@yandex.ru
Subdomains
Mail and authentication
Nameservers
- ns1.example.com
- ns2.example.com
- it-caffe.com
- ns1.it-caffe.com
- ns2.it-caffe.com
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
- ns4.it-caffe.com
- ns3.it-caffe.com
- ns1.topot.tech
- ns2.topot.tech
- ns3.topot.tech
MX records
- mail.it-caffe.com
- mx01.dus.mail.topot.tech
- mx02.hel.mail.topot.tech
SPF policy
- a: it-caffe.com
- mx: it-caffe.com
Threat-feed evidence
History
Related pages
Pivot from it-caffe.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: "it-caffe.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.