Hostname
protegis.com
Last fetched
protegis.com is a hostname indexed by WhisperGraph, the internet-infrastructure graph behind the Whisper Internet Directory. protegis.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
No IPv4 resolution is recorded for protegis.com in WhisperGraph.
IPv6 resolution
No AAAA record for protegis.com is recorded in WhisperGraph.
WHOIS identity
- Registrar
- iana:2
- Registrant organisation
- this domain was caught by dropcatch.com
- Contact emails
- ax4q56bh2jf@networksolutionsprivateregistration.com, d62xf6se2pj@networksolutionsprivateregistration.com, dn8cb6ah8xs@networksolutionsprivateregistration.com, domains@hugedomains.com, e23bx58p7hh@networksolutionsprivateregistration.com, fr9z837s8eg@networksolutionsprivateregistration.com, kw7g95tw7qy@networksolutionsprivateregistration.com, ky6hk7498tw@networksolutionsprivateregistration.com, marketing@protegis.com, r75fu2zd7s2@networksolutionsprivateregistration.com, support@dropcatch.com, ww9754mn2b3@networksolutionsprivateregistration.com
Subdomains
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- ns21.worldnic.com
- ns22.worldnic.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
MX records
- protegis-com.mx1.arsmtp.com
- protegis-com.mx2.arsmtp.com
Threat-feed evidence
History
Related pages
Pivot from protegis.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: "protegis.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.