Skip to content

Hostname

mysecuresign.net

Last fetched

mysecuresign.net resolves to 58.26.203.141, announced in 58.26.192.0/18 by TTSSB-MY - TM TECHNOLOGY SERVICES SDN. BHD. in MY. mysecuresign.net 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 · mysecuresign.netRouting diversity1.5/10Peering density8.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint6.9/10canon.whisper.security/host/mysecuresign.net

Resolution chain

IPv6 resolution

No AAAA record for mysecuresign.net is recorded in WhisperGraph.

Attribution

tm sdn bhd

ORIGIN_AS

WHOIS identity

Registrar
iana:69
Registrant organisation
siliconnet technologies sdn. bhd.
Contact emails
adminsupport@snt.com.my

Subdomains

Mail and authentication

Nameservers

  • ns1.sains.com.my
  • ns2.sains.com.my
  • ns3.sains.com.my
  • ns4.sains.com.my
  • ns5.sains.com.my
  • ns.mysecuresign.net
  • ns1.mysecuresign.net
  • ns2.mysecuresign.net
  • ns3.mysecuresign.net
  • ns4.mysecuresign.net

MX records

  • mx11.mysecuresign.net
  • mx14.mysecuresign.net
  • mx16.mysecuresign.net
  • mx19.mysecuresign.net

SPF policy

  • include: spf-a.mysecuresign.net

Threat-feed evidence

History

Related pages

Pivot from mysecuresign.net 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: "mysecuresign.net"})-[: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.