Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 2 years ago

IP Address Tracking Web APP Built Using Tailwind, Parcel and vanillaJS

tailwind-css, parcel
Abdullah Ayoola•1,080
@abdullah43577
A solution to the IP Address Tracker challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I loved every bit of this project, I just don't know why I just feel like I've got a super power having learnt how to work with APIs and make ajax requests.

It's just so awesome. I implemented another ajax request in this project, but there was a little twist in the ajax request made, if you want to know what the twist is you can check out my solution via GitHub.

but if you do check out the live site, you'll notice that you can make requests using ipv4/ipv6 addresses and that doesn't exclude searching using domain names such as google.com, twitter.com.

well, all in all, let me know what you feel about this project, I was also thinking of working with the localStorage API to store user recent searches in an object of some sort, I might later implement it, you may never know, keep checking out.

Happy Coding to all Developers out there. You may never know how close you're to securing your first developer job, Keep Coding.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Abdullah Ayoola's solution.

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit 1st-party linked stylesheets, and styles within <style> tags.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.