Hostname
flirttactic.com
Last fetched
flirttactic.com resolves to 34.149.78.157, announced in 34.148.0.0/14 by GOOGLE-CLOUD-PLATFORM - Google LLC in US. flirttactic.com is listed by 2 threat feeds; reconciled level HIGH.
Threat posture
50threat score (procedure-native scale)
HIGHListed by 2 threat feeds. At least one source recommends blocking.
- Threat feeds listing this
- 2
- Verdict coverage
- malicious-evidenced
- First seen on a feed
- Wed, 26 Aug 2026 14:49:47 GMT
- Last seen on a feed
- Mon, 14 Sep 2026 23:25:39 GMT
Nutrition Label
Resolution chain
- 34.149.78.157
34.148.0.0/14 · GOOGLE-CLOUD-PLATFORM - Google LLC · Kansas City, US
IPv6 resolution
No AAAA record for flirttactic.com is recorded in WhisperGraph.
Attribution
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:1387
- Registrant organisation
- white mountain online solutions b.v.
- Contact emails
- ac1c0f4aed@flirttactic.com.whoistrustee.com, info@domain-contact.org, 48117c68070b6b50c981230fbfd3f10785f969c1786de23f966d57a40bead256@flirttactic.com.whoisproxy.org, 7a4dc334916716cf362300e9714099b7d87405b46122592882bf7c67df0422c0@flirttactic.com.whoisproxy.org, a2300b3abd3a07e817054f856c840465a8668aa5dc240e2a9237fb901f8a5d61@flirttactic.com.whoisproxy.org, b9b8dbde2c09a1fadce296cc15f2f5f6cd7b0fec9893171aa8c249b14ae2e3a8@flirttactic.com.whoisproxy.org
Subdomains
Mail and authentication
Nameservers
- ns1.dnsimple.com
- ns3.dnsimple.com
- ns1.dnsimple-edge.com
- ns3.dnsimple-edge.io
- ns2.dnsimple-edge.net
- 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.dnsimple-edge.org
MX records
- mx1.jammingjackalope.com
SPF policy
- include: spf.boldschelley.com
- include: spf.jammingjackalope.com
- include: 136224628.spf2.netcorecloud.net
Threat-feed evidence
History
Related pages
Pivot from flirttactic.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: "flirttactic.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.