Skip to content

Hostname

intimtur.com

Last fetched

intimtur.com resolves to 138.249.135.12, announced in 138.249.135.0/24 by PebbleHost-Customers - PebbleHost Ltd in GI. intimtur.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 · intimtur.comRouting diversity2.4/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/intimtur.com

Resolution chain

IPv6 resolution

Attribution

pebblehost

ORIGIN_AS

WHOIS identity

Registrar
iana:228
Registrant organisation
moniker privacy services
Contact emails
06c94edb31fea3c0b31575022c5e82a21bdb9bae42ff88f1067e3e0603908716@intimtur.com.whoisproxy.org, 0f9fbf0fdbf2d8cac1e97197d97e57315fd8f3031096ea0f15b11418a3bf3422@intimtur.com.whoisproxy.org, 19e2cd3db0a865872163c94357d81bc7ff3ccc8177557cda2ae866e38170b215@intimtur.com.whoisproxy.org, 37be8663203de241f73487b92a974eed1ed2ebfb77c09ffda83e0a7612865d45@intimtur.com.whoisproxy.org, 72f17402b298a3b489f80c96cc0dcdc972c181cd2a75249a6b108b8e3cefb761@intimtur.com.whoisproxy.org, 919117317667adf1915db698c989431044cc5889e6819f60842ddc8430959ab8@intimtur.com.whoisproxy.org, 94464f7386f6049eaf04f9074043b6346b45caf51c73c1f5ad79b11ddad28abc@intimtur.com.whoisproxy.org, aa0ad4e27c9fe2590393a8583b85c882ecd90e42e0c9aa76c61509eb3a9af56a@intimtur.com.whoisproxy.org, ab92f9311056531d95a7dc6d3a822adecf8ec0fb7c18bcea2ce32e463f338c00@intimtur.com.whoisproxy.org, d0cc561bdd85d952b0e780ae087ccc7e3b3b3320feb6afced6820d28c685c474@intimtur.com.whoisproxy.org, df8f5a20f4cba4c46ceb85bee5ff0fcdd759c4c73efc1e06a809dee7aa0b1751@intimtur.com.whoisproxy.org, e1a1d0a3111501c40acf4303b27a1c9d4e5b582e4110e0dbe888822ea8f0f83c@intimtur.com.whoisproxy.org

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

  • carter.ns.cloudflare.com
  • meadow.ns.cloudflare.com

Threat-feed evidence

History

Related pages

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