Skip to content

Hostname

guitarnick.com

Last fetched

guitarnick.com resolves to 188.114.96.3, announced in 188.114.96.0/24 by CLOUDFLARENET - Cloudflare, Inc. in CA. guitarnick.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · guitarnick.comRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint7.6/10canon.whisper.security/host/guitarnick.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:48
Registrant organisation
nicola mandorino
Contact emails
mandorino@virgilio.it

Subdomains

Subdomain
autodiscover.guitarnick.com
cpanel.guitarnick.com
cpcalendars.guitarnick.com
cpcontacts.guitarnick.com
mail.guitarnick.com
webdisk.guitarnick.com
webmail.guitarnick.com
www.guitarnick.com

Showing 8 of 8 subdomains (8 per page).

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

Sample outbound links

Mail and authentication

Nameservers

  • eve.ns.cloudflare.com
  • neil.ns.cloudflare.com
  • ns1.mysecurecloudhost.com
  • ns2.mysecurecloudhost.com
  • ns3.mysecurecloudhost.com
  • ns4.mysecurecloudhost.com
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • f.root-servers.net
  • h.root-servers.net
  • k.root-servers.net
  • m.root-servers.net

MX records

  • mail.guitarnick.com

SPF policy

  • include: spf.antispamcloud.com
  • a: guitarnick.com
  • mx: guitarnick.com
  • include: spf.mysecurecloudhost.com
  • include: relay.mailchannels.net
  • ip: 192.250.227.37
  • ip: 198.38.83.198
  • ip: 198.38.86.117
  • ip: 204.93.178.24
  • ip: 204.93.196.26

Threat-feed evidence

History

Related pages

Pivot from guitarnick.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: "guitarnick.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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.